fix: improve error handling in history table #18504
Draft
+50
−14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/
Summary
fix: improve error handling in history table
As a logging service, the history table should avoid exiting on recoverable errors. For issues such as storage being full or temporary network problems with storage, the system should keep retrying until the external service is healthy again.
fix:
COPY INTO
should withMAX_FILES
copy optionIf a lot of intermediate logging files stored in stage, the
COPY INTO
operation should enable aMAX_FILES
option to avoid error:Commit limit reached: 15,000 files for 'copy into table'
Tests
Type of change
This change is